Redistribution of operating environments for the redeployment of grid clients

ABSTRACT

A client-server network environment is temporarily transformed into a grid computing environment through the deployment of a network-booted grid operating system to each of a plurality of network clients. Each participating client operates in the client-server mode under a local operating system. At an appropriate time, a server transmits to each client a thin-client boot image (a dynamically built customized image or an image obtained from a store of predefined boot images) along with a grid application for which the thin-client has been optimized for peak performance. Each client re-boots using the thin-client image, thereby entering the grid mode and executing the grid application.

RELATED APPLICATION DATA

The present Application is a Continuation of U.S. patent application Ser. No. 14/011,460, filed on Aug. 27, 2013, which is a Continuation of U.S. patent application Ser. No. 11/111,028, filed on Apr. 21, 2005, both of which are incorporated herein by reference in their entirety.

TECHNICAL FIELD

The present invention relates generally to the temporary transformation of a conventional client-server environment into a grid computing environment and, more particularly, to the deployment of a network-booted grid operating system to each of a plurality of network clients.

BACKGROUND ART

One path in the evolution of computer networks is the concept of “grid computing” in which computing resources are pooled or shared for the purpose of running a particular application (or set of applications). Thus, large amounts of computing resources are available to work collaboratively on a processing-intensive problem. For example, in a project for the Search for Extra-Terrestrial Intelligence (SETI), thousands of people have “donated” the idle time of their personal computers. Radio signals are gathered by radio telescopes and provided to the online computers through the internet. The computers process the data and return results back to a SETI server in an attempt to identify artificially generated radio signals from space.

Businesses also use grids for more practical purposes, such as in aircraft design or genetic research. Rather than purchase a supercomputer (or lease time on such a computer), a company may find it more economical to establish a grid of less expensive and, individually less powerful, computers. One grid configuration may comprise an array of high availability, enterprise-class computers. However, such a system will typically be cost prohibitive for all but the largest businesses. Another grid configuration may comprise a networked array of personal computer (PC) clients which execute grid applications while the PC's are also being used by the end user. A significant disadvantage of such a configuration is that, for critical grid processing tasks, the overhead associated with sharing resources on a PC client that is already in use severely impacts processing performance, both for the end user and for the grid application.

Consequently, a need remains for a grid configuration which is cost efficient for small and medium sized users.

SUMMARY OF THE INVENTION

The present invention computer network having a client-server mode and a grid mode through the deployment of a network-booted grid operating system to each of a plurality of network clients. Each participating client operates in the client-server mode under a local operating system. At an appropriate time, a server transmits to each client a thin-client boot image (a dynamically built customized image or an image obtained from a store of predefined boot images) along with a grid application for which the thin-client has been optimized for peak performance. Each client re-boots using the thin-client image, thereby entering the grid mode and executing the grid application.

Other method and server apparatus embodiments are provided herein and supply related advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a network of the present invention in a client-server mode;

FIG. 2 is a block diagram of a client device of the present invention operating in the client-server mode;

FIG. 3 is a block diagram of a server of the present invention;

FIG. 4 is a block diagram of a client device of the present invention operating in the grid mode;

FIG. 5 is a block diagram of a network of the present invention in a grid mode; and

FIGS. 6A and 6B are a flowchart of a method of the present invention.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of a network 100 of the present invention in a client-server mode. A plurality of client devices 110A, 110B, 110C and 110D (collectively referred to herein as 110) are coupled, such as through a router 120 or other similar networking device to a server 130. The invention may also be implemented with other types of networks, including the internet.

FIG. 2 is a block diagram of one of the client devices 110A (representative of all client devices 110) of the present invention operating in the client-server mode of FIG. 1. In the client-server mode, the client device 110A executes software applications 112 under a local operating system 114. For example, the client device 110A may be a conventional desktop or notebook personal computer (PC) operating under a Microsoft® Windows® operating system although other types of computers, such as workstations, and other operating systems, such as Linux®, may be used. The client 110A also includes one of a variety of possible communications protocols 116 to enable the client 110A and the server 130 to communicate with each other and exchange data in various forms. Additionally, the client 110A preferably also includes a protocol or routine, such as the Intelliboot agent (also known as a pre-execution environment or PXE) to allow the client 110A to boot from a network-supplied boot image, such as the thin-client image 512.

The server 130 is illustrated in the block diagram of FIG. 3 and includes a processor 132 and a memory 134 for storing instructions executable by the processor 132. For clarity, the memory 134 is illustrated as a single element. However, the actual memory 134 used in the server may include RAM, ROM, flash, magnetic, optical or any combination of these or other forms of memory. In the embodiment illustrated, the server 130 is a dynamic host configuration protocol (DHCP) server. In such a configuration, the server 130 further includes a DHCPD configuration file 134 and a client information database 138, either or both of which may reside in the memory 134. A grid manager 140 comprises a set of instructions executable by the processor 132 for managing the operation of the network 100 in a grid mode. A boot image module 142 also comprises a set of instructions executable by the processor 132 for, in one embodiment, generating a boot image or, in a second embodiment, storing predetermined boot images. Both the grid manager 140 and the boot image module 142 may reside in the memory 134 along with one or more grid applications 146. A communications protocol 116B allows the exchange of data with a client 110A through the communications protocol 116A residing in the client 110A. The server 130 may run under any suitable operating system which allows the server 130 to deploy the thin-client image 512 to the clients 110. Red Hat Linux 9 is one such operating system and permits client usage and grid processing status to be monitored.

In operation, the server 130 transmits to each available client 110 a thin-client image 512 from the boot image module 142 and a grid application 146. Using the thin-client image 512, each client 110 re-boots in a grid mode and launches the grid application 146 (FIG. 4). The thin-client image 412 may be, for example, PXES Linux Thin Client and includes only enough operating system for the client 110 to run the grid application 146 without the memory and processor resources of the client being used for unnecessary overhead processes such as managing unused, peripheral drivers, idle applications, and desktop environments. Moreover, a thin-client such as PXES allows a user at the server 130 to customize the features which the client 110 will use. FIG. 5 illustrates the network in the grid mode 500. The server 130 operates now as a master node 530 and is able to acquire the use of substantially all of the computing resources (memory and processor) of each client 110, which are now considered to be processing nodes 510 on the grid 500. At some later time, the master node 530 directs that the processing nodes 510 terminate current grid operations and re-boot either in a new grid image with a different grid application or in their respective local operating systems 114, whereupon the grid mode 500 reverts to the client-server mode 100 (FIGS. 1 and 2) and all prior client applications and data will be restored to the state in which the user left them.

The operating system image is used to provide a minimal base environment on top of which the grid application runs and can be highly customized to provide only the necessary applications for supporting the needs of the various grid applications. Since the network booted operating system is typically run out of the client's system memory from what is called a “RAM disk”, removing any operating system features and applications from the image provides more RAM disk capacity for the operation of the grid task. Moreover, as the total image decreases in size, the tasks required to generate the image dynamically and boot it over a network will take less time to complete. For example, while transferring a single image of 5 MB may take only a matter of seconds, transferring a 5 MB image to each of potentially tens of thousands of nodes could take considerably longer as the server system and the network increasingly become a bottle neck. If the image can instead be reduced from 5 MB to 3.5 MB, a deployment speed gain may be attained which is proportional to the decrease in the image size. Benefits of using a thin-client environment and tools such as those provided by the PXES project include the flexibility and speed of piecing together the grid operating environment on-the-fly using simple parameters such as system type and application prerequisites to describe the scenario for deployment. The server would need to contain at least two sets or tables of information mapping the host type to a list of required drivers needed to boot a very basic network enabled operating system, as well as a second set or table of information describing the package prerequisites needed to support the grid application.

In one embodiment of the transformation from the client-server mode to the grid mode, the clients 110 are re-booted with the thin-client image in the grid mode at a predetermined time when the clients 110 are not likely to be used in the usual course of their operations. For example, the transformation to the grid mode may be initiated after normal business hours, after the day-to-day activities of the clients 110 has substantially ceased. Subsequently, the processing nodes 510 may then be re-booted into their local operating systems in the client-server mode before normal business hours resume. Thus, the present invention reduces idle resources in the environment 100 by using clients 110 at a time during which they might not otherwise be utilized.

A method of the present invention will now be described with reference to the flowchart of FIGS. 6A and 6B. Upon the occurrence of a predefined event, a client 110 may initiate the transformation process (step 600). Such an event may include, but not be limited to, reaching a particular time of day (such as after normal business hours) or the client 110 being idle for a predetermined period of time. Alternatively, the transformation to the grid mode may be initiated by the server 130, such as at a particular time of day or by sending out periodic inquiries to the clients 110 to determine if any have been idle for a predetermined period of time. If enough clients 110 are idle to provide desired grid resources, the transformation process may be initiated.

A participating client 110A transmits its media access control (MAC) address to the server 130, along with its current IP address and hostname (step 602). Based on this identification information, the server 130 determines from the client information database 138 if a thin-client or boot image 512 for the host type of the particular client 110A is already stored in the DHCP configuration file 136 on the server 130 (step 604). If not, the boot image module 142 of the sever 130 generates an image 512 for the client 110A (step 606). Alternatively, the server 130 may not store any predefined images but generate a new image 512 for each client 110 at the beginning of each transformation process, thereby omitting the determination step 604. The server 130 next updates the DHCP configuration file 136 with the MAC address, hostname and image (if the latter has changed and requires an update) of the client 110A and the client information database 138 with the IP address and hostname of the client 110A (step 608). The status of the client 110A is also updated in the client information database 138 by changing the status from “client” to “grid”.

The server 130 reinitializes the DHCP service (step 610) in order to commit the configuration updates and makes the image 512 available to the client 110A via the TFTP protocol as required by the PXE boot protocol (step 612). With both the server 130 and the client 110A prepared for the boot process, the server 130 initiates a reboot of the client 110A (step 630). The client 110A will have been configured to attempt booting first from its network device (step 614) and then from local devices if the network boot is not successful and times out. If during the client 110A boot process the server 130 does not fulfill the client 110A network boot request (step 616), the client's 110A network boot process times out and the client 110A continues to the next device in the boot order and loads its local operating system 114, returns to its previously cached state and waits for a next re-boot (step 618). If the client 110A is made aware of an available image 512 by the server 130 defined for the DHCP service 136 the client 110A will proceed to boot the image provided by the server 130 (step 620). The server 130 may then remove the client entry from the DHCP configuration file 136 (step 622) in order to maintain a clean DHCP configuration. The client 110A, using the communications protocol 116 or other type of startup script launches the grid application 146 (step 624) and the client begins functioning as a grid processing node 510A.

Preferably, the thin-client image 512 transmitted to each client 110 is dynamically built or generated image and customized for the particular hardware and operating system configuration of each client 110. Thus, a variety of different types of computers, running under a variety of different operating systems, may be included the grid environment 500. Moreover, because a thin-client image 512 is preferably individually transmitted to a client 110A rather than being broadcast to all clients 110, different grid applications 146 may be transmitted to different clients 110 allowing different processing nodes 510 to work on different computing problems simultaneously.

At a later predetermined time, such as before normal business hours resume or upon completion of a computing project, the master node 530 initiates the removal of the processing node 510A from the grid environment 500 (step 626) and updates the client information database 138 to reflect the changed status of the processing node 510A (step 628). The master node 530 then initiates a re-boot of the processing node 510A (step 630) and the routine returns to step 616 at which time the client 110A again attempts to boot from the network and times out if the server 130 does not provide an image and proceeds to the next available boot device defined in the client 130 boot order sequence.

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

While one or more embodiments of the present invention have been illustrated in detail, the skilled artisan will appreciate that modifications and adaptations to those embodiments may be made without departing from the scope of the present invention as set forth in the following claims. 

What is claimed is:
 1. A method for temporarily transforming a client-server network into a grid network, comprising: allowing each of a plurality of client devices to operate under a local operating system in a client-server mode; at a first predetermined time, configuring a server, with which the client devices are coupled through a network, to operate under a thin-client operating system, whereby the server becomes a master node on the network; for each client device: determining whether a boot image is available for deployment to the client device; after determining that a boot image is not available for the client device, generating a boot image for the client device; directing that the client device initiate a network boot in a thin-client mode, whereby the client device becomes a processing node for the server; transmitting a thin-client image and a grid application to the processing node, whereupon the client device boots the thin-client image; and launching the grid application on the processing node, whereby the processing node operates in a grid mode for use by the grid application, the grid application able to launch different grid applications on different processing nodes.
 2. The method of claim 1, further comprising, at a second, later predetermined time, directing that each processing node re-boot into its respective local operating system.
 3. The method of claim 1, wherein the plurality of client devices comprise personal computers.
 4. The method of claim 1, wherein the thin-client operating system comprises a Linux thin-client operating system.
 5. A server coupled to a plurality of client devices through a computer network, each client operating in a respective local operating system in a client-server mode, the server operable to: direct that each client device initiate at a first predetermined time, whereupon each client device attempts to perform a network boot; upon successful network boot by each client device, transmit thin-client images to the respective client devices, whereupon each client device boots the thin-client image; and direct that each client device launch a grid application, whereby each client device operates in a grid mode for use by the grid application, the grid application able to launch different grid applications on different processing nodes.
 6. The server of claim 5, wherein the server is further operable to, at a second predetermined time, direct that each client device re-boot without providing a thin-client image, whereupon a network boot fails and each client-device boots from a local device into its respective local operating system, whereby the client devices operate in a client-server mode.
 7. The server of claim 5, wherein the server is further operable to generate a dynamically built customized thin-client image for each of the client devices.
 8. The server of claim 5, wherein the server is further operable to: at least one predefined thin-client image; and transmit a selected one of the predefined thin-client images to each client device.
 9. The server of claim 5, wherein: the server is further operable to receive from each client a MAC address, a current IP address, and a hostname of the client; and the server further comprises: a configuration file for storing the MAC address, the hostname, and the thin-client image for each client; and a client information database for storing the MAC address, the current IP address, a system type, the hostname, and an updated status of each client, the status selected from the group comprising client mode and grid mode.
 10. The server of claim 5, wherein the thin-client mode comprises a Linux thin-client operating system mode.
 11. A method for reducing idle computing resources on a network, comprising: operating a plurality of clients under a local operating system in a client-server mode on a network; performing a network boot of each client in a thin-client mode at a first predetermined time; receiving a thin-client image and a grid application in each client from a master node, whereby each client operates in a grid mode; and launching the grid application in each client, the grid application able to launch different grid applications on different processing nodes.
 12. The method of claim 11, further comprising re-booting each client into the local operating system in the client-server mode at a second, later predetermined time.
 13. The method of claim 11, wherein receiving a thin-client image comprises receiving a dynamically built customized thin-client image for each client.
 14. The method of claim 11, further comprising receiving at each client a selected one of a plurality of predefined thin-client images. 